第一次看此系列文的朋友，請先移步到 Day 1 – 如何開始？進行方式、自我介紹實戰 哦！

🎬 情境故事

面試中，考官常會問：「你能分享一個專案經驗嗎？」這時候很多人會腦中一片空白，不知道要從技術細節開始，還是先講專案目標。若只說「我用 Go 寫 API」就太淺，但如果一下子講到太細的 code，也會讓對方跟不上。

今天的目標：練習用簡單的架構，分享處理過的一個專案。

🤖 Config Prompt

[Config]
- Day: Day2 – Project Experience Sharing
- Scenario: Job interview — describing a past backend engineering project.

👉 在練習之前...

先選擇一個專案，想一下：

1. 專案目標是什麼（需求）
2. 我負責什麼（角色）
3. 用了什麼技術（技術細節）
4. 達成什麼成果（指標）

並且把關鍵字寫下來。

我的關鍵字：

1. Optimize the login and register API
2. Main developer
3. Goroutine and MySQL Index
4. TPS from 600 to 3000+

🎯 開始進行練習

在 GPT 開啟新對話、貼上 Prompt，然後進入語音模式開始練習吧！

昨天我發現，貼完 Prompt 他會馬上用文字問問題。這時候進入語音，說：「Sorry. What was your question?」，他就用語音說一次了。

結束對話之後，記得聽他把 Report 說完在結束對話。這樣才能看得到整個 Report 的文字。

記得把對話錄下來，自己聽一次，想想有哪裡不自然。

📌 小技巧

因為這次我們說的比較多，他的 feedback 會給很長，很難照著說。

你可以請他把 feedback 一句一句講。

Can you separate the sentence to small parts. One sentence per time, Please.

這個我再試試可以怎麼調整 Prompt 來達到這個效果。

🆘 今日救命句

• 救命句（簡短切入專案）：

  I worked on a backend project for...

• 爭取思考時間：

  Let me think for a moment...

🔑 核心句型

1. 專案目標 / Context

• The goal of the project was to ...

The goal of the project was to improve system performance.

• Our project aimed to ...

Our project aimed to build a high-throughput trading system.

• The main purpose was to ...

The main purpose was to make the service more scalable.

2. 我的角色 / Role

• I was responsible for ...

I was responsible for designing the backend architecture.

• My role focused on ...

My role focused on database optimization and API performance.

• I mainly worked on ...

I mainly worked on integrating Kafka with microservices.

3. 技術細節 / Contribution

• I implemented a XXX to XXX.

I implemented an in-memory order book to reduce latency.

• I optimized the XXX to XXX.

I optimized the API to handle 100k requests per second.

• I designed a XXX to XXX.

I designed a gRPC service to replace a slower REST API.

4. 成果 / Result

• As a result, ...

As a result, the latency was reduced by 40%.

• We achieved ...

We achieved stable performance even under heavy load.

• The system could handle 5x more traffic after my changes.

📝 我的今日反饋

今天我得到的反饋比較多，所以我又多練習了一次。
我發現我在說的時候會忽略 to+動詞 這個文法，反而說到 for 的時候會停頓，然後後面接著講動詞。

在第二次對話的時候，我試著在說 to/for 之前停頓思考。我自己感覺說起話來順很多。

Per-turn Corrections
	•	Turn 3: You said, “I was main developer responsible for developing all features.”
You mean: “I was the main developer responsible for developing all the features.”
Alternative: “I was the lead developer handling all the feature development.”

Top 3 Patterns
	1.	Article usage: Sometimes missing “the” before nouns. Just remember: if it’s a specific thing, pop in “the.”
	2.	Plural endings: Make sure to add “s” for plurals like “features.”
	3.	Prepositions: Tiny words like “for” or “in” can be tricky. A simple rule: use “for” before a goal (like “for improving performance”).

Phrase Pack
	•	“I was the main developer on this project.”
	•	“The goal was to improve API performance.”
	•	“I optimized it using goroutines and indexes.”
	•	“As a result, performance increased significantly.”
	•	“I was responsible for all the feature development.”
	•	“We boosted TPS from 600 to over 3,000.”

Intonation Tip

Focus on emphasizing key numbers or results. For example, stress “600” and “3,000” to highlight the improvement.

Fluency & Pronunciation Notes
	1.	You did well with short sentences.
	2.	Your pacing was good and clear.
	3.	Keep practicing those small grammar fixes; you’re improving.
	4.	You sounded natural and confident by the end.
	5.	Overall, nice job with the corrections!

Key Focus for Next Time
	1.	Work on article usage and plural forms.
	2.	Practice stressing key results in a sentence.
	3.	Try a quick 3-minute drill summarizing a project in three short steps: intro, what you did, and the result.